Tier-based admission control for user equipment

ABSTRACT

A device may receive information associated with a network resource request. The network resource request may be a request, by a user device, for access to a network resource associated with a network. The device may determine a subscriber class associated with the user device based on receiving the information associated with the network resource request. The device may determine a service type associated with the network resource request based on receiving the information associated with the network resource request. The device may determine an allocation and retention priority (ARP) level based on the determined subscriber class and the determined service type. The device may assign the ARP level to the network resource.

BACKGROUND

User devices, such as smart phones, may be allocated network resources.During periods of network congestion, network resources may be limited.An allocation and retention priority (“ARP”) parameter may be used tocontrol congestion by differentiating users based on a priority level.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2;

FIG. 4 is a flow chart of an example process for assigning a Quality ofService (QoS) parameter to a requested network resource based on asubscriber class associated with a user device requesting the networkresource;

FIGS. 5A and 5B are diagrams of an example implementation relating tothe example process shown in FIG. 4;

FIG. 6 is a flow chart of an example process for enforcing admissioncontrol to a network resource based on a service type requested by auser device, a Quality of Service parameter, and/or a network congestionlevel; and

FIGS. 7A and 7B are diagrams of an example implementation relating tothe example process shown in FIG. 6.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

A radio access network (“RAN”) provider may reserve radio resources,such as resources associated with a long term evolution (“LTE”) network,a code division multiple access (“CDMA”) network, or the like, for useduring periods of network congestion. The network provider maydifferentiate a resource request based on assignment of a priorityparameter, such as an allocation and retention priority (“ARP”) level.An ARP level may be associated with one or more Quality of Service(“QoS”) parameters (e.g., one or more parameters associated withtreatment of a traffic flow). A higher ARP level (e.g., level 1) may beassociated with a more preferred status than a lower ARP level (e.g.,level 9) during allocation of bearers when the network is congested.

However, the RAN provider may wish to exercise more granular control forcongestion management by allowing access and assigning more resources toa preferred subscriber class of users (e.g., associated with userdevices). Tier-based network resource allocation may be used to providepreferential access to a network resource based on user subscriptionpriority (e.g., a subscriber class), and may provide greater granularityof control during network congestion. Implementations described hereinmay assist a base station in managing the allocation of networkresources during periods of network congestion based on a user'ssubscription class, retention capabilities, and/or network congestionlevels.

FIG. 1 is a diagram of an overview of an example implementation 100described herein. As shown in FIG. 1, example implementation 100 mayinclude a user device, a base station, a policy and charging rulesfunction device (“PCRF”), a home subscriber server (“HSS”), and anetwork. For example implementation 100, the user device may include amobile phone, the base station may include an eNodeB (“eNB”), the PCRFmay include one or more servers, the HSS may include one or moreservers, and the network may include an LTE network.

As shown in FIG. 1, the base station may receive a request from the userdevice to be allocated one or more network resources associated with thenetwork. For example, the base station may receive a request for aquantity of bearers (e.g., with a particular resource allocation, suchas a guaranteed bit rate (“GBR”) resource allocation, a non-guaranteedbit rate (“non-GBR”) resource allocation, a physical resource blockresource allocation, a connection resource allocation, or the like) tohandle network traffic of a particular service type, such as voicetraffic, mobile internet traffic, short message service (“SMS”) traffic,multimedia messaging service (“MMS”) traffic, or the like. The basestation may determine a network congestion level (e.g., a utilizationlevel) associated with the network, and may determine to process thenetwork resource request from the user device using tier-based admissioncontrol procedures, as described herein.

As further shown in FIG. 1, the PCRF may be notified (e.g., by the basestation) of the resource request and/or the service type requested bythe user device, and may receive subscriber class information (e.g.,high, medium, low), associated with the user device, from the HSS. ThePCRF may assign, to the network resource (e.g., the bearer) requested bythe user device, one or more quality of service (“QoS”) parameters(e.g., an ARP level, a pre-emption capability, a pre-emptionvulnerability, a QoS Class Indicator (“QCI”) value, etc.) based on thesubscriber class associated with the user device and/or the service typerequested by the user device. For example, a high subscriber class userdevice may receive a high priority ARP level and a low subscriber classuser device may receive a low priority ARP level.

As further shown in FIG. 1, the PCRF may provide the one or more QoSparameters to the base station. The base station may configure admissioncontrol based on the QoS parameters (e.g., the ARP level), the servicetype, and/or the network congestion level. For example, assuming acongested network, the base station may allocate a requested quantity ofnetwork resources (e.g., physical resource blocks for GBR resources) toa bearer that has been assigned a high priority ARP level; may allocatea requested quantity of network resources to a bearer that has beenassigned a medium priority ARP level; and may bar a bearer that has beenassigned a low priority ARP level from accessing any network resources.In this way, the base station may manage service during networkcongestion by reserving network resources for premium users duringperiods of network congestion.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods described herein may be implemented. As shown in FIG. 2,environment 200 may include a user device 210, a base station 220, ahome subscriber server (“HSS”) 230, a network 240, and a policy andcharging rules function (“PCRF”) 250. Devices of environment 200 mayinterconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

User device 210 may include one or more devices capable of connecting toa network, such as network 240 (e.g., via base station 220), andutilizing a network resource, such as one or more bearers. For example,user device 210 may include a mobile phone (e.g., a smart phone), aradiotelephone, a personal communications system (“PCS”) terminal (e.g.,that may combine a cellular radiotelephone with data processing and datacommunications capabilities), a personal digital assistant (“PDA”)(e.g., that may include a radiotelephone, a pager, Internet/intranetaccess, etc.), a computer (e.g., a desktop computer, a laptop computer,a tablet computer, etc.), a personal gaming system, and/or anothersimilar type of device. In some implementations, user device 210 maysend, to base station 220, information that identifies user device 210,information that identifies a service type requested by user device 210,information that identifies a network resource requested by user device210, or the like.

Base station 220 may include one or more devices capable of receiving,generating, processing, storing, and/or transmitting network traffic,such as media, audio, video, text, and/or other traffic, destined forand/or received from user device 210. In some implementations, basestation 220 may include an eNodeB associated with an LTE network thatreceives traffic from and/or sends traffic to network 240 via a packetdata network gateway and/or a serving gateway. Additionally, oralternatively, one or more base stations 220 may be associated with aRAN other than an LTE network. For example, base station 220 may beassociated with a CDMA evolution data-optimized (“EV-DO”) network, aCDMA 1x radio transmission technology (“RTT”) network, a Wi-Fi network,a WiMax network, or the like. Base station 220 may send traffic toand/or receive traffic from user device 210 via an air interface. Insome implementations, base station 220 may receive information, fromPCRF 250, identifying a QoS parameter, such as an ARP level, associatedwith a network resource, such as a bearer, requested by user device 210.

HSS 230 may include one or more devices capable of receiving,generating, processing, storing, and/or providing subscriberinformation, such as a user identifier, authentication and/orauthorization information, a user's internet protocol (“IP”)information, subscriber class information associated with user device210, or the like. For example, HSS 230 may include a user profile serverfunction (“UPSF”), a home location register (“HLR”), an authenticationcenter (“AuC”), a server, or the like. HSS 230 may transmit subscriberclass information to PCRF 250 via network 240, in some implementations.

Network 240 may include one or more wired and/or wireless networks. Forexample, network 240 may include a cellular network, a public landmobile network (“PLMN”), a first generation (“1G”) network, a secondgeneration (“2G”) network, a third generation (“3G”) network, a fourthgeneration (“4G”) network, a fifth generation (“5G”) network, a CDMA onetimes transmission (“1x”) network, a CDMA EV-DO network, an LTE network,and/or another network. Additionally, or alternatively, network 240 mayinclude a Wi-Fi network, a local area network (“LAN”), a wide areanetwork (“WAN”), a metropolitan area network (“MAN”), a telephonenetwork (e.g., the Public Switched Telephone Network (“PSTN”)), an adhoc network, an intranet, the Internet, a fiber optic-based network,and/or a combination of these or other types of networks.

PCRF 250 may include one or more network devices capable of providingnetwork control regarding service data flow detection, gating, QoS,and/or flow-based charging. Policies and rules regarding QoS may includepolicies and rules instructing user device 210 and/or base station 220to minimize packet loss, to implement a packet delay budget, to providea guaranteed bit rate (GBR) service, to provide a non-guaranteed bitrate (non-GBR) service, to provide a particular latency, and/or toperform other activities associated with QoS. PCRF 250 may providepolicies and rules to other network devices, such as base station 220,HSS 230, or the like, to implement network control. PCRF 250 maydetermine how a certain service data flow shall be treated within abearer, and may ensure that QoS is in accordance with a user's profileand/or network policies. PCRF 250 may determine one or more QoSparameters (e.g., an ARP level, a QCI value, etc.) based on a subscriberclass and/or a service type associated with user device 210, and mayassign the QoS parameters to a network resource.

The number of devices and networks shown in FIG. 2 is provided as anexample. In practice, there may be additional devices and/or networks,fewer devices and/or networks, different devices and/or networks, ordifferently arranged devices and/or networks than those shown in FIG. 2.Furthermore, two or more devices shown in FIG. 2 may be implementedwithin a single device, or a single device shown in FIG. 2 may beimplemented as multiple, distributed devices. Additionally, one or moreof the devices of environment 200 may perform one or more functionsdescribed as being performed by another one or more devices ofenvironment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to user device 210, base station 220, HSS 230, and/orPCRF 250. Additionally, or alternatively, each of user device 210, basestation 220, HSS 230, and/or PCRF 250 may include one or more devices300 and/or one or more components of device 300. As shown in FIG. 3,device 300 may include a bus 310, a processor 320, a memory 330, aninput component 340, an output component 350, and a communicationinterface 360.

Bus 310 may include a component that permits communication among thecomponents of device 300. Processor 320 may include a processor (e.g., acentral processing unit, a graphics processing unit, an acceleratedprocessing unit), a microprocessor, and/or any processing component(e.g., a field-programmable gate array (“FPGA”), an application-specificintegrated circuit (“ASIC”), etc.) that interprets and/or executesinstructions. Memory 330 may include a random access memory (“RAM”), aread only memory (“ROM”), and/or another type of dynamic or staticstorage device (e.g., a flash, magnetic, or optical memory) that storesinformation and/or instructions for use by processor 320.

Input component 340 may include a component that permits a user to inputinformation to device 300 (e.g., a touch screen display, a keyboard, akeypad, a mouse, a button, a switch, etc.). Output component 350 mayinclude a component that outputs information from device 300 (e.g., adisplay, a speaker, one or more light-emitting diodes (“LEDs”), etc.).

Communication interface 360 may include a transceiver-like component,such as a transceiver and/or a separate receiver and transmitter, thatenables device 300 to communicate with other devices, such as via awired connection, a wireless connection, or a combination of wired andwireless connections. For example, communication interface 360 mayinclude an Ethernet interface, an optical interface, a coaxialinterface, an infrared interface, a radio frequency (“RF”) interface, auniversal serial bus (“USB”) interface, a Wi-Fi interface, a cellularnetwork interface, or the like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes in response to processor 320 executingsoftware instructions included in a computer-readable medium, such asmemory 330. A computer-readable medium may be defined as anon-transitory memory device. A memory device may include memory spacewithin a single physical storage device or memory space spread acrossmultiple physical storage devices.

Software instructions may be read into memory 330 from anothercomputer-readable medium or from another device via communicationinterface 360. When executed, software instructions stored in memory 330may cause processor 320 to perform one or more processes describedherein. Additionally, or alternatively, hardwired circuitry may be usedin place of or in combination with software instructions to perform oneor more processes described herein. Thus, implementations describedherein are not limited to any specific combination of hardware circuitryand software.

The number of components shown in FIG. 3 is provided as an example. Inpractice, device 300 may include additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 3.

FIG. 4 is a flow chart of an example process 400 for assigning a Qualityof Service parameter to a requested network resource based on asubscriber class associated with a user device requesting the networkresource. In some implementations, one or more process blocks of FIG. 4may be performed by PCRF 250. Additionally, or alternatively, one ormore process blocks of FIG. 4 may be performed by another device or agroup of devices separate from or including PCRF 250, such as basestation 220 and/or HSS 230.

As shown in FIG. 4, process 400 may include receiving a request,associated with a user device, for a network resource associated with anetwork (block 410). For example, base station 220 may receive a requestfrom user device 210 to be allocated a network resource associated withnetwork 240, and may provide information associated with the resourcerequest to PCRF 250. In some implementations, the network resource mayinclude a radio capacity resource, a radio access bearer, guaranteed bitrate (“GBR”) bandwidth, non-guaranteed bit rate (“non-GBR”) bandwidth, aconnection resource, or the like.

The request for a network resource may include information associatedwith determining a QoS parameter for the requested network resource. AQoS parameter may include, for example, an ARP level, a GBR parameter, anon-GBR parameter, a pre-emption capability, a pre-emptionvulnerability, a QoS Class Indicator (“QCI”) value, or the like. Forexample, PCRF 250 may receive (e.g., from base station 220) a userdevice identifier that identifies a user device 210 requesting thenetwork resource (e.g., an international mobile subscriber identity(“IMSI”), a mobile equipment identifier (“MEID”), a telephone number, orthe like). Additionally, or alternatively, PCRF 250 may receive (e.g.,from base station 220) information that identifies a service typerequested by a user device 210 requesting the network resource. Aservice type may include, for example, an internet service, a voiceservice, a video service, a messaging service, etc.

As further shown in FIG. 4, process 400 may include determiningsubscriber class information associated with the user device (block420). For example, PCRF 250 may receive subscriber class informationfrom HSS 230, in some implementations. A subscriber class may include aclassification (e.g., high or low; high, medium, or low; high, mediumhigh, medium, medium low, or low; etc.) of user device 210 that maycorrelate to the preferentiality of user device 210 in being grantednetwork resources by base station 220. In some implementations, PCRF 250may transmit a user device identifier to HSS 230, and HSS 230 maydetermine subscriber class information based on the user deviceidentifier (e.g., by searching a data structure). HSS 230 may transmitthe subscriber class information to PCRF 250. Additionally, oralternatively, PCRF 250 may search a data structure for the subscriberclass information (e.g., using the user device identifier).

As further shown in FIG. 4, process 400 may include assigning a QoSparameter to the network resource based on the subscriber classinformation and/or a service type requested by the user device (block430). For example, PCRF 250 may assign a QoS parameter indicating a highpreferentiality in receiving network resources to the network resourcerequest by user device 210 when user device 210 is associated with ahigh subscriber class. A QoS parameter may include a QoS class indicator(“QCI”) value, an ARP parameter value (e.g., an ARP value indicative ofan ARP level), a guaranteed bit rate (“GBR”) parameter value, anon-guaranteed bit rate (“non-GBR”) parameter value, a maximum bit rate(“MBR”) parameter value, or the like.

PCRF 250 may map one or more subscriber classes to one or more ARPparameter values, in some implementations. For example, when ARPparameter values range from 1 to 15 (e.g., with 1 being the highestpriority value), PCRF 250 may reserve ARP parameter values 1 and 2 forspecial uses (e.g., an emergency use, a testing use, etc.), may assignARP parameter values 3 and 4 to high priority subscribers, may assignARP parameter values 5 and 6 to medium priority subscribers, may assignARP parameter values 7 and 8 to low priority subscribers, and may assignARP parameter values 9 to 15 for regular traffic flow use by generalusers and/or low priority service types (e.g., low priorityapplications).

PCRF 250 may assign a QoS parameter to a network resource based on aservice type requested by a user device, in some implementations. Forexample, network resources associated with different service types(e.g., internet services, enterprise/business services, peer-to-peerservices, voice services, video services, gaming services, interactiveservices, etc.) may be assigned different QoS parameters.

As further shown in FIG. 4, process 400 may include providing the QoSparameter (block 440). For example, PCRF 250 may bind the QoS parameterto a network resource requested by user device 210. In someimplementations, PCRF 250 may provide information identifying the QoSparameter to devices of network 240 (e.g., base station 220, a packetdata network gateway (“PGW”), a serving gateway (“SGW”), a mobilitymanagement entity (“MME”), a policy and charging enforcement function(“PCEF”), or the like). For example, PCRF 250 may provide informationthat identifies the QoS parameter to base station 220 for use inadmission control.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, differentblocks, fewer blocks, or differently arranged blocks than those depictedin FIG. 4. Additionally, or alternatively, two or more of the blocks ofprocess 400 may be performed in parallel.

FIGS. 5A and 5B are diagrams of an example implementation 500 relatingto process 400 shown in FIG. 4. As shown in FIG. 5A, and by referencenumber 510, assume that base station 220 receives a request for abearer, from user device 210. As shown by reference number 520, basestation 220 determines a network congestion level associated withnetwork 240, an LTE network. For example, assume that base station 220determines network congestion to be 83% for network 240. Assume thatbecause the 83% network congestion level associated with network 240exceeds a threshold level of 80%, network 240 is congested (e.g., above80%). As shown by reference number 530, base station 220 providesresource request information (e.g., information identifying therequested resource and/or user device 210) to PCRF 250. As shown byreference number 540, PCRF 250 receives subscriber class informationfrom HSS 230 (e.g., based on providing a user device identifier to HSS230). For example, user device 210 may be identified as having asubscriber class of high, medium, or low.

As shown in FIG. 5B, and by reference number 550, PCRF 250 determinesone or more QoS parameters (e.g., an ARP level) to assign to the bearerrequested by user device 210, and binds the QoS parameters (e.g., theARP level, a QCI value, a data rate control, etc.) to the bearer. PCRF250 assigns the ARP level based on a pre-configured determination, asshown by reference number 560. Assume that ARP levels 1 and 2 arereserved for allocation based on factors other than subscriber class(e.g., emergency service personnel, network testing, etc.), and furtherassume that ARP levels 9-15 are reserved for traffic from customerslacking a subscriber class and/or for low priority services. Thisallocation of ARP levels is provided as an example, and otherallocations are possible.

As an example, assuming that user device 210 is a very high priorityuser device, user device 210 may be assigned an ARP level of 3 or 4. Asanother example, assuming that user device 210 is a high priority userdevice, user device 210 may be assigned an ARP level of 5 or 6. Asanother example, assuming that user device 210 is a medium priority userdevice, user device 210 may be assigned an ARP level of 7 or 8. Asanother example, assuming that user device 210 is a low priority userdevice, user device 210 may be assigned an ARP level between 9-15,inclusive. This assignment of ARP levels is provided as an example, andother assignments are possible.

As shown by reference number 570, PCRF 250 provides the assigned QoSparameters (e.g., information identifying the assigned ARP level) tobase station 220. Base station 220 may use the QoS parameters whenenforcing admission control, as described in more detail elsewhereherein.

As indicated above, FIGS. 5A and 5B are provided merely as an example.Other examples are possible and may differ from what was described withregard to FIGS. 5A and 5B.

FIG. 6 is a flow chart of an example process 600 for enforcing admissioncontrol to a network resource based on a service type requested by auser device, a Quality of Service parameter, and/or a network congestionlevel. In some implementations, one or more process blocks of FIG. 6 maybe performed by base station 220. Additionally, or alternatively, one ormore process blocks of FIG. 6 may be performed by another device or agroup of devices separate from or including base station 220, such asHSS 230 and/or PCRF 250.

As shown in FIG. 6, process 600 may include determining a service typerequested by a user device (block 610). For example, base station 220may receive information identifying a service type requested by userdevice 210. User device 210 may send information, to base station 220,requesting access to a network resource for a connection associated witha particular service type. The service type may include, for example, aninternet service, an enterprise/business service, a peer-to-peerservice, a voice service, a video service, a gaming service, andinteractive service, or the like.

As shown in FIG. 6, process 600 may include receiving a QoS parameterassociated with a request, by the user device, for a network resource ofa network (block 620). For example, base station 220 may receiveinformation identifying a QoS parameter associated with a request byuser device 210 for a network resource (e.g., a bearer with a particularresource allocation). In some implementations, base station 220 mayreceive the QoS parameter from PCRF 250 for the service type requestedby user device 210. For example, PCRF 250 may determine one or more QoSparameters (e.g., an ARP level and/or parameter value, a QCI value, aGBR parameter value, a non-GBR parameter value, an MBR parameter value,etc.) for the requested network resource, and may provide informationidentifying the one or more QoS parameters to base station 220 (e.g., onone or more bearers for providing the service).

As further shown in FIG. 6, process 600 may include determining anetwork congestion level associated with the network (block 630). Forexample, base station 220 may determine the network congestion levelassociated with network 240, and may determine that the networkcongestion level satisfies a threshold. In some implementations, thethreshold may trigger usage of subscriber class information indetermining access admission for a user device to a network. In someimplementations, the network congestion level may be based on ameasurable network resource. The measurable network resource may includea quantity of allocated bearers, a quantity of user devices 210connected to the network and/or in communication with base station 220,a bandwidth capacity, a throughput rate, or the like. For example, basestation 220 may determine the network congestion level associated withnetwork 240 based on a percentage of bearers allocated out of a totalquantity of available bearers.

The measurable network resource may be associated with a networkresource requested by user device 210, in some implementations. Forexample, base station 220 may determine the threshold level at whichnetwork 240 may be considered congested, and the threshold level may bea utilization level of the requested resource. In some implementations,the measurable network resource may be different from the requestednetwork resource.

Base station 220 may determine that the network congestion levelsatisfies the threshold based on a discrete quantity of the measurablenetwork resource, in some implementations. For example, base station 220may determine that network 240 is congested when a quantity of bearershave been allocated. Additionally, or alternatively, base station 220may determine that network 240 is congested when a quantity of bearersremain available.

Base station 220 may determine that the network congestion levelsatisfies a threshold based on a percentage associated with themeasurable network resources, in some implementations. For example, basestation 220 may determine that network 240 is congested when aparticular percentage of the maximum throughput rate is being achieved.

As further shown in FIG. 6, process 600 may include selectivelyproviding the user device with access to the network resource based onthe service type, the QoS parameter, and/or the network congestion level(block 640). For example, base station 220 may provide user device 210with access to the network resource (e.g., associating one or morephysical resource blocks with a requested bearer) based on the ARP levelassociated with the requested bearer. Additionally, or alternatively,base station 220 may remove user device 210 from the network (e.g., maydisconnect, pre-empt, and/or remove access to the network resource). Forexample, when the network congestion level exceeds a threshold, basestation 220 may enforce a QoS parameter (e.g., an ARP level) by denyingaccess to the network resource by a low ARP level user device 210.

Base station 220 may determine whether to assign the network resource touser device 210 based on comparing the network congestion level to oneor more admission thresholds, in some implementations. An admissionthreshold may be based on a percentage of radio capacity resources, aquantity of users, a quantity of bearers, or the like. For example, basestation 220 may determine an admission threshold based on a percentageutilization of radio capacity. In this case, when base station 220determines admission thresholds correlating to three subscriber classes(e.g., high, medium, and low; each subscriber class correlating to arange of ARP levels, such as the high subscriber class correlating toARP levels 1-4, the medium subscriber class correlating to ARP levels5-8, and the low subscriber class correlating to ARP levels 9-15), basestation may assign the requested resource to user device 210 when thenetwork congestion level satisfies a first admission threshold (e.g., isbelow the first admission threshold), and when user device 210 isdetermined to be of a high, medium, or low subscriber class.

Additionally, or alternatively, base station 220 may assign therequested resource to user device 210 when the network congestion levelsatisfies a second admission threshold (e.g., higher than the firstadmission threshold), and when user device 210 is determined to be of ahigh or medium subscriber class. Additionally, or alternatively, basestation 220 may assign the requested resource to user device 210 whenthe network congestion level satisfies a third admission threshold(e.g., higher than the first and second admission thresholds), and whenuser device 210 is determined to be of a high subscriber class. In someimplementations, user device 210 may bar all new user devices 210 fromthe network when the congestion level is beyond the third admissionthreshold.

A single admission threshold may apply to multiple subscriber classes,in some implementations. For example, base station 220 may determinethat either a low or medium priority user device 210 (e.g., where PCRF250 has assigned an ARP level to the resource request associated withuser device 210 based on determining user device 210 to be of either alow or medium subscriber class) is to be denied requests for resourceallocations when the network congestion level exceeds a single admissionthreshold.

Base station 220 may provide access to the network resource based on aservice type, in some implementations. A service type may include, forexample, an emergency call, a messaging service, a voice service, avideo service, or the like. For example, base station 220 may determinethat the request for the network resource is to be denied based on theARP level and the network congestion level. In this case, base station220 may determine that the service type is an emergency call, and mayprovide access to the network resource accordingly.

Base station 220 may provide access to the network resource when userdevice 210 is being handed-off from another base station, in someimplementations. A hand-off may occur when user device 210 is movingfrom an area covered by a first base station 220 to an area covered by asecond base station 220. In this case, the second base station 220 mayafford treatment associated with a higher subscriber class (e.g., ahigher ARP level) to user device 210 in order to avoid a serviceinterruption (e.g., dropping a call).

Base station 220 may provide access to the network resource based on oneor more access rules, in some implementations. An access rule may be apreset determination by base station 220 as to whether user device 210is to be allocated network resources based on a given set of factors.For example, an access rule may determine whether to allocate networkresources to user device 210 at a particular network congestion level,using a particular subscriber class, using a particular QoS parameter(e.g., an ARP level), for a particular service type, etc.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 may include additional blocks, differentblocks, fewer blocks, or differently arranged blocks than those depictedin FIG. 6. Additionally, or alternatively, two or more blocks of process600 may be performed in parallel.

FIGS. 7A and 7B are diagrams of an example implementation 700 relatingto process 600 shown in FIG. 6. As shown in FIG. 7A, and by referencenumber 710, user device 210 sends a request to establish a bearer (e.g.,with access to a quantity of a network resource) to base station 220. Asshown by reference number 720, base station 220 determines the networkcongestion level (e.g., 85%) associated with network 240 (e.g., an LTEnetwork). As shown by reference number 730, base station 220 receives aQoS parameter (e.g., an ARP level) from PCRF 250, determined asdiscussed herein in connection with FIG. 4. Assume the QoS parameterincludes an ARP level.

As shown in FIG. 7B, base station 220 stores access rule 740 (e.g., aset of pre-configured determinations to be used for determining whetherto grant access to a particular network resource at a particular ARPlevel and a particular network congestion level). As shown by referencenumber 750, base station 220 assigns access to the network resource bycomparing the ARP level associated with the network resource request andthe network congestion level associated with network 240 against thepre-configured determinations. For example, based on the networkcongestion level of 85%, base station 220 would deny user device 210access to the network resource (e.g., based on access rule 740) if PCRF250 assigned an ARP of 10-15.

As another example, assuming that base station 220 had determined thenetwork congestion level to be 95%, base station 220 would deny accessto the network resource (e.g., based on access rule 740) if PCRF 250 hadassigned an ARP of 5-15.

As indicated above, FIGS. 7A and 7B are provided merely as an example.Other examples are possible and may differ from what was described withregard to FIGS. 7A and 7B.

Implementations described herein may allow a PCRF to assign ARP levelsbased on a subscriber class associated with a user device. Furthermore,a base station may manage network congestion using tier-based networkresource allocation control based on the assigned ARP levels and/or thenetwork congestion level. In so doing, the base station may allocatenetwork resources to preferred users during periods of congestion.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in conjunction withthresholds. As used herein, satisfying a threshold may refer to a valuebeing greater than the threshold, more than the threshold, higher thanthe threshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, etc. Furthermore,some of these phrases, as used herein, may be used interchangeably.

It will be apparent that systems and/or methods, as described herein,may be implemented in many different forms of software, firmware, andhardware in the implementations illustrated in the figures. The actualsoftware code or specialized control hardware used to implement thesesystems and/or methods is not limiting of the implementations. Thus, theoperation and behavior of the systems and/or methods were describedwithout reference to the specific software code—it being understood thatsoftware and hardware can be designed to implement the systems and/ormethods based on the description herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Where onlyone item is intended, the term “one” or similar language is used.Further, the phrase “based on” is intended to mean “based, at least inpart, on” unless explicitly stated otherwise.

What is claimed is:
 1. A device, comprising: one or more processors to:receive, from a user device, a network resource request, the networkresource request being a request to be allocated a network resourceassociated with a network; determine a network congestion levelassociated with the network; receive information identifying anallocation and retention priority (ARP) level associated with thenetwork resource request and the user device, the ARP level beingdetermined based on a subscriber class associated with the user device;and selectively assign the network resource to the user device based onthe network congestion level and the ARP level.
 2. The device of claim1, where the one or more processors are further to: determine aplurality of admission thresholds, the plurality of admission thresholdsbeing associated with different threshold levels of network congestion;and where the one or more processors, when selectively assigning thenetwork resource to the user device, are further to: selectively assignthe network resource to the user device further based on the pluralityof admission thresholds.
 3. The device of claim 1, where the one or moreprocessors are further to: determine that the network resource is anon-guaranteed bit rate resource; determine a non-guaranteed bit rateutilization based on determining that the network resource is anon-guaranteed bit rate resource; and where the one or more processors,when selectively assigning the network resource to the user device, arefurther to: selectively assign the network resource to the user devicebased on the non-guaranteed bit rate resource utilization.
 4. The deviceof claim 1, where the one or more processors are further to: determine abearer utilization; where the one or more processors, when determiningthe network congestion level, are further to: determine the networkcongestion level based on the bearer utilization; and where the one ormore processors, when selectively assigning the network resource to theuser device, are further to: selectively assign the network resourcebased on the bearer utilization.
 5. The device of claim 1, where the oneor more processors are further to: determine a service type associatedwith the network resource request; and where the one or more processors,when selectively assigning the network resource to the user device, arefurther to: selectively assign the network resource to the user devicebased on the service type.
 6. The device of claim 1, where the one ormore processors are further to: determine a plurality of ARP levelsassociated with an admission threshold; determine that the ARP levelassociated with the network resource request matches at least one of theplurality of ARP levels associated with the admission threshold; andwhere the one or more processors, when selectively assigning the networkresource to the user device, are further to: selectively assign thenetwork resource to the user device based on determining that the ARPlevel associated with the network resource request matches at least oneof the plurality of ARP levels associated with the admission threshold.7. The device of claim 1, where the one or more processors are furtherto: determine that the user device is undergoing a hand-off from a basestation; determine that the network resource request by the user deviceis associated with a network resource being used by the user deviceundergoing the hand-off; and where the one or more processors, whenselectively assigning the network resource to the user device, arefurther to: selectively assign the network resource to the user devicebased on determining that the network resource request is associatedwith the network resource being used by the user device undergoing thehand-off.
 8. A method, comprising: receiving, by a device, a networkresource request, the network resource request corresponding to arequest, by a user device, to be allocated a network resource associatedwith a network; determining, by the device, a network congestion levelassociated with the network; providing, by the device, a user deviceidentifier that identifies the user device; receiving, by the device andbased on providing the user device identifier, information identifying aquality of service parameter assigned to the network resource, thequality of service parameter being determined based on a subscriberclass identified using the user device identifier; and selectivelyassigning, by the device, the network resource to the user device basedon the network congestion level and the quality of service parameter. 9.The method of claim 8, where receiving the information identifying thequality of service parameter further comprises: receiving informationidentifying an allocation and retention priority (ARP) parameter value,the ARP parameter value being determined based on at least one of: thesubscriber class associated with the user device, or a service typeassociated with the network resource request.
 10. The method of claim 8,further comprising: determining a plurality of admission thresholds, theplurality of admission thresholds being associated with differentthreshold levels of network congestion; and where selectively assigningthe network resource to the user device further comprises: selectivelyassigning the network resource to the user device based on the pluralityof admission thresholds.
 11. The method of claim 8, further comprising:determining that the network resource is a guaranteed bit rate resource;determining a guaranteed bit rate utilization based on determining thatthe network resource is a guaranteed bit rate resource; and wheredetermining the network congestion level associated with the networkfurther comprises: determining the network congestion level based on theguaranteed bit rate utilization.
 12. The method of claim 8, furthercomprising: determining a service type associated with the networkresource request; and where selectively assigning the network resourceto the user device further comprises: selectively assigning the networkresource to the user device based on the service type.
 13. The method ofclaim 8, where selectively assigning the network resource to the userdevice further comprises: denying the user device access to the networkresource based on the network congestion level and the quality ofservice parameter.
 14. The method of claim 8, where the user device is afirst user device; and where the method further comprises: adjustingaccess to another network resource for a second user device based onreceiving the network resource request; and where selectively assigningthe network resource to the user device further comprises: selectivelyassigning the network resource to the first user device based onadjusting access to the other network resource for the second userdevice.
 15. The method of claim 8, where determining the networkcongestion level further comprises determining the network congestionlevel based on at least one of: a guaranteed bit rate utilization; anon-guaranteed bit rate utilization; a bearer utilization; a physicalresource block utilization; or a quantity of user devices incommunication with the device that receives the network resourcerequest.
 16. A computer-readable medium storing instructions, theinstructions comprising: one or more instructions that, when executed byone or more processors, cause the one or more processors to: receiveinformation associated with a network resource request, the networkresource request being a request, by a user device, for access to anetwork resource associated with a network; determine a subscriber classassociated with the user device based on receiving the informationassociated with the network resource request; determine a service typeassociated with the network resource request based on receiving theinformation associated with the network resource request; determine anallocation and retention priority (ARP) level based on the determinedsubscriber class and the determined service type; and assign the ARPlevel to the network resource.
 17. The computer-readable medium of claim16, where the one or more instructions, that cause the one or moreprocessors to assign the ARP level to the network resource, furthercause the one or more processors to: provide information identifying theARP level, providing the information identifying the ARP level causingthe ARP level to be assigned to the network resource.
 18. Thecomputer-readable medium of claim 17, where the one or moreinstructions, that cause the one or more processors to provide theinformation identifying the ARP level, further cause the one or moreprocessors to: provide the information identifying the ARP level to abase station.
 19. The computer-readable medium of claim 17, where thenetwork resource is a bearer; and where the one or more instructions,that cause the one or more processors to provide the informationidentifying the ARP level, further cause the one or more processors to:provide the information identifying the ARP level via the bearer. 20.The computer-readable medium of claim 16, where the one or moreinstructions, that cause the one or more processors to determine thesubscriber class associated with the user device, further cause the oneor more processors to: receive information identifying the user device;provide the information identifying the user device to another device;receive, from the other device, information identifying the subscriberclass based on providing the information identifying the user device;and determine the subscriber class based on receiving the informationidentifying the subscriber class.